Skip to main content

This is a new service – your feedback will help us to improve it.

Liverpool City Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

Allerton Beeches

reference
TPO220.A1
name
Allerton Beeches
tree-preservation-order

undefined

TPO220
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.900873 53.379632,-2.900990 53.379681,-2.900952 53.379692,-2.900933 53.379693,-2.901028 53.379743,-2.901029 53.379732,-2.901037 53.379717,-2.901091 53.379746,-2.901298 53.379844,-2.901339 53.379804,-2.901400 53.379831,-2.901357 53.379872,-2.901496 53.379936,-2.901712 53.380040,-2.901728 53.380045,-2.901740 53.380046,-2.901750 53.380045,-2.901773 53.380039,-2.901779 53.380039,-2.901787 53.380042,-2.901830 53.380064,-2.901835 53.380068,-2.901838 53.380075,-2.901841 53.380093,-2.901845 53.380098,-2.901854 53.380104,-2.902291 53.379719,-2.902432 53.379593,-2.902290 53.379286,-2.902245 53.379184,-2.902179 53.379041,-2.902254 53.378970,-2.902434 53.378810,-2.902026 53.378760,-2.901946 53.378747,-2.901842 53.378728,-2.901792 53.378717,-2.901587 53.378667,-2.901562 53.378660,-2.901509 53.378638,-2.901375 53.378568,-2.901315 53.378541,-2.901275 53.378526,-2.901227 53.378503,-2.901053 53.378441,-2.900860 53.378369,-2.900816 53.378362,-2.900755 53.378349,-2.900708 53.378336,-2.899855 53.379163,-2.900418 53.379426,-2.900553 53.379491,-2.900864 53.379637,-2.900873 53.379632)))
point
POINT (-2.901271 53.379186)
notes
The several tree of whatever species situated within area A1 on map.
entry-date
1990-04-10
start-date
1990-06-25
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Liverpool City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL